Initiating Signaling in Mobile Management Entity Pools Using Workflows

ABSTRACT

Concepts and technologies are disclosed herein for initiating signaling in mobile management entity pools using workflows. A processor can execute an orchestrator application. The processor can receive location data that indicates a geographic location at which a virtual mobility management entity has been instantiated and registered. The processor can obtain a mobility management entity topology that defines boundaries of two or more mobile management entity pools and identify, based on the location data, one of the mobility management entity pools in which the virtual mobility management entity is located. The processor can identify pool elements included in the mobility management entity pool, obtain a workflow for establishing and configuring the pool elements, and request establishment of signaling between the virtual mobile management entity and the pool elements.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of and claims priority to U.S. patentapplication Ser. No. 14/878,364, entitled “Initiating Signaling inMobile Management Entity Pools Using Workflows,” filed Oct. 8, 2015, nowallowed, which is incorporated herein by reference in its entirety.

BACKGROUND

In mobility networks, physical network function (“PNF”) based networkelements may be added to networks and provisioned through a process thatmay take hours or even days to complete based on the number of elementsbeing instantiated, deployment configurations associated with theelements, and the like. In some instances, by the time a new PNF isactivated on a network, the original need for the PNF may no longerexist. For example, an evolving network function may be provided by aversion of PNFs deployed to a network. A particular version of the PNFmay be obsolete when deployment is completed, in some cases, due to arapidly evolving network, or the like.

In a long term evolution (“LTE”) or LTE-Advanced network, a mobilemanagement entity (also referred to as a “mobility management entity” or“MME”) can include a centralized node. The mobile management entity canhandle signaling procedures for mobile devices, for example. The mobilemanagement entity can be deployed in standalone or pooledconfigurations. When deployed in pools, only specific eNodeBs in apredefined geographic area associated with the pools may establishsignaling connections to the mobile management entities. Establishingthe signaling can be a process that can take hours or even days tocomplete due to manual provisioning of the network by systemadministrators.

SUMMARY

The present disclosure is directed to initiating signaling in mobilemanagement entity pools using workflows. A server computer or othercomputing device can execute an orchestrator application or otherfunctionality for providing the functionality illustrated and describedherein. A virtual mobile management entity can be instantiated forvarious purposes such as, for example, supporting particularfunctionality for a network, to meet demand changes associated with thenetwork, to provide a new function to users, to change quality ofservice levels associated with particular resources, combinationsthereof, or the like. The virtual mobile management entity can beregistered with a network, and a request such as an activation requestor other request can be generated to inform the orchestrator application(or other functionality) that the virtual mobile management entity hasbeen instantiated and registered. The activation request also canspecify a geographic location associated with the virtual mobilemanagement entity.

The orchestration application can analyze the activation request toidentify the geographic location of the virtual mobile managemententity. The orchestration application can query or otherwise search alocation database based on the determined geographic location. In someembodiments, the orchestrator application can generate virtual mobilemanagement entity data that can capture the geographic location andsubmit the virtual mobile management entity data to the locationdatabase. The orchestrator application can receive or otherwise obtain aresult set or other results. The results or result set can identify oneor more entities associated with the geographic location associated withthe virtual mobile management entity. The identified elements caninclude other pool elements associated with the location of the virtualmobile management entity and therefore can include pool elements and/orpeer nodes associated with the virtual mobile management entity. Theorchestrator application also can obtain workflows and/or configurationsthat can specify how signaling is to be established for the identifiedpeer nodes (or other pool elements) and the virtual mobile managemententity.

The orchestrator application can forward the workflows to variousentities associated with the mobile management entity pool in which thevirtual mobile management entity was instantiated. In some embodiments,for example, the workflows can be sent to one or more element managementsystem (“EMS”) entities associated with the network. The signalingbetween the virtual mobile management entity and the peer nodes can beestablished by one or more EMS entities using the workflows, if desired,and the signaling and/or peer nodes also can be configured based onconfiguration information that can be included with or as a part of theworkflows. Thus, embodiments of the concepts and technologies describedherein can enable setup of signaling for virtual mobile managemententities using geographic location information associated with a newlyinstantiated virtual mobile management entity. These and additionalfeatures of the concepts and technologies described herein will beillustrated and described in more detail below.

According to one aspect of the concepts and technologies disclosedherein, a method is disclosed. The method can include receiving, by aprocessor that can execute an orchestrator application, location datathat can indicate a geographic location at which a virtual mobilitymanagement entity has been instantiated and registered. The method alsocan include obtaining, by the processor, a mobility management entitytopology that defines boundaries of two or more mobile management entitypools, identifying, by the processor and based on the location data, aone of two or more mobility management entity pools in which the virtualmobility management entity is located, and identifying, by theprocessor, pool elements included in the one of the two or more ofmobility management entity pools. The method also can include obtaining,by the processor, a workflow for establishing and configuring the poolelements, and requesting, by the processor, establishment of signalingbetween the virtual mobile management entity and the pool elements.

In some embodiments, the location data can be received with a commonlanguage location identifier that can identify the virtual mobilitymanagement entity. In some embodiments, the pool elements can includepeer nodes associated with the virtual mobile management entity. In someembodiments, the workflow can be obtained from an element managementsystem via an application programming interface exposed by the elementmanagement system. In some embodiments, establishing the signaling caninclude sending a further application programming interface call to eachof the elements, the further application programming interface callincluding configuration information used to establish the signaling.

In some embodiments, for example when an eNodeB is mobile and dynamicreconfiguration of mobile management entity pools is desired, the methodalso can include detecting a first geographic location associated withan eNodeB, the eNodeB being associated with the virtual mobilemanagement entity; determining if the first geographic locationassociated with the eNodeB has changed relative to a second geographiclocation associated with the eNodeB, the second geographic locationbeing determined using a location database; and in response todetermining that the first geographic location has changed, identifyinga new mobile management entity pool associated with the first geographiclocation, and adding the eNodeB to the new mobile management entity poolassociated with the first geographic location.

In some embodiments, identifying the new mobile management entity poolcan include mapping the first geographic location to a table stored inthe location database. The table can identify mobile management entitypools and geographic locations associated with the mobile managemententity pools. In some embodiments, the workflow can specify aconfiguration for one of the pool elements and an interface over whichthe signaling is to occur. In some embodiments, the workflow can includea directed graph that can be executed by an element management system toestablish the signaling.

According to another aspect of the concepts and technologies disclosedherein, a system is disclosed. The system can include a processor and amemory. The memory can store computer-executable instructions that, whenexecuted by the processor, cause the processor to perform operations.The operations can include receiving location data that can indicate ageographic location at which a virtual mobility management entity hasbeen instantiated and registered, obtaining a mobility management entitytopology that defines boundaries of two or more mobile management entitypools, identifying, by the processor and based on the location data, aone of two or more mobility management entity pools in which the virtualmobility management entity is located, identifying pool elementsincluded in the one of the two or more mobility management entity pools,obtaining a workflow for establishing and configuring the pool elements,and requesting establishment of signaling between the virtual mobilemanagement entity and the pool elements.

In some embodiments, the pool elements can include peer nodes associatedwith the virtual mobile management entity. In some embodiments, theeNodeB can be mobile. In some embodiments, the computer-executableinstructions, when executed by the processor, cause the processor toperform additional operations. The additional operations can includedetecting a first geographic location associated with an eNodeB, theeNodeB being associated with the virtual mobile management entity;determining if the first geographic location associated with the eNodeBhas changed relative to a second geographic location associated with theeNodeB, the second geographic location being determined using a locationdatabase; and in response to determining that the first geographiclocation has changed, identifying a new mobile management entity poolassociated with the first geographic location, and adding the eNodeB tothe new mobile management entity pool associated with the firstgeographic location.

In some embodiments, identifying the new mobile management entity poolcan include mapping the first geographic location to a database tablestored in the location database. The table can identify mobilemanagement entity pools and geographic locations associated with themobile management entity pools. In some embodiments, the workflow can beobtained from an element management system via an applicationprogramming interface exposed by the element management system. In someembodiments, establishing the signaling can include sending a furtherapplication programming interface call to each of the elements, thefurther application programming interface call including configurationinformation used to establish the signaling.

According to yet another aspect, a computer storage medium is disclosed.The computer storage medium can have computer-executable instructionsstored thereon. When the computer-executable instructions are executedby a processor, the processor can perform operations. The operations caninclude receiving location data that can indicate a geographic locationat which a virtual mobility management entity has been instantiated andregistered; obtaining a mobility management entity topology that definesboundaries of two or more mobile management entity pools; identifying,by the processor and based on the location data, a one of two or moremobility management entity pools in which the virtual mobilitymanagement entity is located; identifying pool elements included in theone of the two or more mobility management entity pools; obtaining aworkflow for establishing and configuring the pool elements; andrequesting establishment of signaling between the virtual mobilemanagement entity and the pool elements.

In some embodiments, the pool elements can include peer nodes associatedwith the virtual mobile management entity. In some embodiments, theeNodeB can be mobile. In some embodiments, the computer-executableinstructions, when executed by the processor, cause the processor toperform additional operations. The additional operations further caninclude detecting a first geographic location associated with an eNodeB,the eNodeB being associated with the virtual mobile management entity;determining if the first geographic location associated with the eNodeBhas changed relative to a second geographic location associated with theeNodeB, the second geographic location being determined using a locationdatabase; and in response to determining that the first geographiclocation has changed, identifying a new mobile management entity poolassociated with the first geographic location, and adding the eNodeB tothe new mobile management entity pool associated with the firstgeographic location.

In some embodiments, identifying the new mobile management entity poolcan include mapping the first geographic location to a table stored inthe location database. The table can identify mobile management entitypools and geographic locations associated with the mobile managemententity pools. In some embodiments, the workflow can be obtained from anelement management computer storage medium via an applicationprogramming interface exposed by the element management computer storagemedium, and establishing the signaling can include sending a furtherapplication programming interface call to each of the elements, thefurther application programming interface call including configurationinformation used to establish the signaling.

Other systems, methods, and/or computer program products according toembodiments will be or become apparent to one with skill in the art uponreview of the following drawings and detailed description. It isintended that all such additional systems, methods, and/or computerprogram products be included within this description, be within thescope of this disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a system diagram illustrating an illustrative operatingenvironment for various embodiments of the concepts and technologiesdescribed herein.

FIG. 2 is a flow diagram showing aspects of a method for initiatingsignaling associated with a virtual mobility management entity,according to an illustrative embodiment of the concepts and technologiesdescribed herein.

FIG. 3 is a flow diagram showing aspects of a method for updatingsignaling associated with a virtual mobility management entity,according to an illustrative embodiment of the concepts and technologiesdescribed herein.

FIG. 4 schematically illustrates an example of an eNodeB moving from afirst geographic location to a second geographic location, according toan example embodiment of the concepts and technologies described herein.

FIG. 5 schematically illustrates a network, according to an illustrativeembodiment of the concepts and technologies described herein.

FIG. 6 is a block diagram illustrating an example computer systemconfigured to initiate and update signaling in mobile management entitypools using workflows, according to some illustrative embodiments of theconcepts and technologies described herein.

FIG. 7 is a line diagram schematically illustrating mapping ofgeographic location information to tables in a location database,according to some illustrative embodiments of the concepts andtechnologies described herein.

DETAILED DESCRIPTION

The following detailed description is directed to initiating signalingin mobile management entity pools using workflows. A server computer orother computing device can execute an orchestrator application or otherfunctionality for providing the functionality illustrated and describedherein. A virtual mobile management entity can be instantiated forvarious purposes such as, for example, supporting particularfunctionality for a network, to meet demand changes associated with thenetwork, to provide a new function to users, to change quality ofservice levels associated with particular resources, combinationsthereof, or the like. The virtual mobile management entity can beregistered with a network, and a request such as an activation requestor other request can be generated to inform the orchestrator application(or other functionality) that the virtual mobile management entity hasbeen instantiated and registered. The activation request also canspecify a geographic location associated with the virtual mobilemanagement entity.

The orchestration application can analyze the activation request toidentify the geographic location of the virtual mobile managemententity. The orchestration application can query or otherwise search alocation database based on the determined geographic location. In someembodiments, the orchestrator application can generate virtual mobilemanagement entity data that can capture the geographic location andsubmit the virtual mobile management entity data to the locationdatabase. The orchestrator application can receive or otherwise obtain aresult set or other results. The results or result set can identify oneor more entities associated with the geographic location associated withthe virtual mobile management entity. The identified elements caninclude other pool elements associated with the location of the virtualmobile management entity and therefore can include pool elements and/orpeer nodes associated with the virtual mobile management entity. Theorchestrator application also can obtain workflows and/or configurationsthat can specify how signaling is to be established for the identifiedpeer nodes (or other pool elements) and the virtual mobile managemententity.

The orchestrator application can forward the workflows to variousentities associated with the mobile management entity pool in which thevirtual mobile management entity was instantiated. In some embodiments,for example, the workflows can be sent to one or more element managementsystem (“EMS”) entities associated with the network. The signalingbetween the virtual mobile management entity and the peer nodes can beestablished by one or more EMS entities using the workflows, if desired,and the signaling and/or peer nodes also can be configured based onconfiguration information that can be included with or as a part of theworkflows. Thus, embodiments of the concepts and technologies describedherein can enable setup of signaling for virtual mobile managemententities using geographic location information associated with a newlyinstantiated virtual mobile management entity. These and additionalfeatures of the concepts and technologies described herein will beillustrated and described in more detail below.

While the subject matter described herein is presented in the generalcontext of program modules that execute in conjunction with theexecution of an operating system and application programs on a computersystem, those skilled in the art will recognize that otherimplementations may be performed in combination with other types ofprogram modules. Generally, program modules include routines, programs,components, data structures, and other types of structures that performparticular tasks or implement particular abstract data types. Moreover,those skilled in the art will appreciate that the subject matterdescribed herein may be practiced with other computer systemconfigurations, including hand-held devices, multiprocessor systems,microprocessor-based or programmable consumer electronics,minicomputers, mainframe computers, and the like.

Referring now to FIG. 1, aspects of an operating environment 100 forvarious embodiments of the concepts and technologies disclosed hereinfor initiating signaling in mobile management entity pools usingworkflows will be described, according to an illustrative embodiment.The operating environment 100 shown in FIG. 1 includes a server computer102. The server computer 102 can operate in communication with and/or aspart of a communications network (“network”) 104, though this is notnecessarily the case.

According to various embodiments, the functionality of the servercomputer 102 may be provided by one or more server computers, desktopcomputers, mobile telephones, laptop computers, set-top boxes, othercomputing systems, and the like. It should be understood that thefunctionality of the server computer 102 can be provided by a singledevice, by two similar devices, and/or by two or more dissimilardevices. For purposes of describing the concepts and technologiesdisclosed herein, the server computer 102 is described herein as aserver computer that includes a processor and a memory. It should beunderstood that this embodiment is illustrative, and should not beconstrued as being limiting in any way.

The server computer 102 can execute an operating system (not shown inFIG. 1) and one or more application programs such as, for example, anorchestrator application 106. The operating system can include acomputer program for controlling the operation of the server computer102. The orchestrator application 106 can include an executable programconfigured to execute on top of the operating system to provide variousfunctions illustrated and described herein for initiating signaling inmobile management entity pools using workflows. In some embodiments, theserver computer 102 also can execute management application or module,though in the illustrated embodiment the management functionality isprovided by the orchestrator application 106. Because the managementfunctionality can be provided by other entities, modules, or the like,it should be understood that the illustrated example embodiment isillustrative and therefore should not be construed as being limiting inany way.

The orchestrator application 106 can be configured to manage one or moremobile management entity (“MME”) pools 108A-N (hereinafter collectivelyand/or generically referred to as “mobile management entity pools 108”),and to instantiate and/or configure one or more components of the mobilemanagement entity pools 108 as illustrated and described in more detailbelow. As shown in FIG. 1, the mobile management entity pools 108 caninclude various components (illustrated only with respect to the mobilemanagement entity pool 108A for the sake of clarity). It should beunderstood that this example is illustrative and therefore should not beconstrued as being limiting in any way.

As shown, one or more of the mobile management entity pools 108 caninclude one or more element management system (“EMS”) entities.According to various embodiments of the concepts and technologiesdescribed herein, the mobile management entity pools 108 can include amobile management entity (“MME”) EMS 110, an eNodeB (“eNB”) EMS 112, andone or more other EMS entities (labeled “other EMS” in FIG. 1) 114.Before describing the functions of these EMS entities, the othercomponents of the mobile management entity pools 108 will be defined.

The mobile management entity pools 108 also can be associated withvarious core elements, which can be part of a core 116. The core 116 caninclude, but is not limited to, one or more broadcast/multicast control(“BMC”) entities; one or more evolved serving mobile location center(“ESLMC”) entities; one or more gateway mobile location center (“GMLC”)entities; one or more mobile switching center (“MSC”) entities; one ormore dynamic resource allocation (“DRA”) entities; one or more homesubscriber server (“HSS”) entities; and/or other entities. Because thefunction of the core 116 and/or the various elements of the core 116 aregenerally understood, these elements will not be further describedherein.

The mobile management entity pools 108 also can include a pool ofvirtual mobile management entities 118A-N (hereinafter collectivelyand/or generically referred to as “virtual mobile management entities118”). As shown in FIG. 1, the virtual mobile management entity 118N islabeled as a “new virtual mobile management entity.” This designationwill be further understood with reference to the description herein. Itshould be understood, however, that the new virtual mobile managemententity 118N can be substantially similar (or even identical) to thevirtual mobile management entity 118A, and that the word “new” can beused solely to refer to a recent instantiation of the new virtual mobilemanagement entity 118N and/or a recent addition of the virtual mobilemanagement entity 118N to a mobile management entity pool 108. It shouldbe understood that this example is illustrative and therefore should notbe construed as being limiting in any way.

The mobile management entity pools 108 also can include one or moreeNodeBs (“eNBs”) 120A-N (hereinafter collectively and/or genericallyreferred to as “eNodeBs 120”). According to various embodiments of theconcepts and technologies described herein, the virtual mobilemanagement entities 118 can serve as control nodes for one or more ofthe eNodeBs 120. The virtual mobile management entities 118 also canprovide and/or include other functionality and therefore can beprovisioned at various times to the enhance features of a network inwhich the virtual mobile management entities 118 are provisioned. As isgenerally understood, network operators can design networks with virtualmobile management entity 118 overlap, e.g., eNodeBs 120 can be served byone or more virtual mobile management entities 118 in some embodiments,though this is not the case. Thus, it can be appreciated that aparticular virtual mobile management entity 118 may serve one or moreeNodeBs 120 and/or that a particular eNodeB 120 may be served by one ormore virtual mobile management entities 118. The eNodeBs 120 can provideradio access to various devices, as is generally understood.

According to various embodiments of the concepts and technologiesdescribed herein, the new virtual mobile management entity 118N can beinstantiated at some time. As mentioned above, the new virtual mobilemanagement entity 118N may be instantiated to add functionality to anetwork, to add control functionality to a mobile management entity pool108, and/or for other reasons such as meeting a demand increase(detected or expected), detecting movement of radio resources (e.g.,eNodeBs 120) in a network, or the like.

According to various embodiments of the concepts and technologiesdescribed herein, the mobile management entity EMS 110 can receive orotherwise obtain a virtual mobile management entity activationindication (“activation indication”) 122. The activation indication 122can indicate, to the mobile management entity EMS 110 that the newvirtual mobile management entity 118N is activated. According to variousembodiments, the activation indication 122 also can include geographiclocation information (e.g., latitude and longitude coordinates)associated with the new virtual mobile management entity 118N. It shouldbe understood that this example is illustrative and therefore should notbe construed as being limiting in any way.

The mobile management entity EMS 110 can create and route an activationrequest 124 (labeled “request 124” in FIG. 1) to the server computer102. The activation request 124 also can request instantiation ofsignaling between the new virtual mobile management entity 118N andother elements of the mobile management entity pool 108. According tovarious embodiments of the concepts and technologies described herein,the activation request 124 can include virtual mobile management entitylocation data (labeled “VMME location data” in FIG. 1). The virtualmobile management entity location data can indicate the geographiclocation associated with the new virtual mobile management entity 118Nand therefore can be determined from the activation indication 122, insome embodiments. In some embodiments, the virtual mobile managemententity location data can indicate a geographic location of a host of thenew virtual mobile management entity 118N. This information can be usedfor various purposes, as will be explained in more detail below. Theactivation request 124 also can include data that can indicate that thenew virtual mobile management entity 118N has been instantiated andregistered. It should be understood that this example is illustrativeand therefore should not be construed as being limiting in any way.

The server computer 102 (e.g., via execution of the orchestratorapplication 106) can receive the activation request 124. In someembodiments, the activation request 124 can be received by theorchestrator application 106 via an application programming interface(“API”) 126. The API 126 can be exposed by the server computer 102, insome embodiment. Because the activation request 124 can be obtained bythe orchestrator application 106 in other manners and/or via otherinterfaces, it should be understood that this embodiment is illustrativeand therefore should not be construed as being limiting in any way.

The orchestrator application 106 also can extract, from the activationrequest 124, various types of information and/or data relating to thenew virtual mobile management entity 118N. The orchestrator application106 can package this information as the virtual mobile management entitydata 128 (labeled “vMME data 128” in FIG. 1). The orchestratorapplication 106 also can provide the virtual mobile management entitydata 128 to a location database 130 (labeled “location DB 130” in FIG.1).

According to various embodiments of the concepts and technologiesdescribed herein, the location database 130 can be stored at a datastorage device such as the data store 132. The functionality of the datastore 132 can be provided by one or more databases, server computers,desktop computers, mobile telephones, laptop computers, other computingsystems, and the like. In the illustrated embodiments, the functionalityof the data store 132 is provided by a server computer that hosts thelocation database 130. It should be understood that this example isillustrative and therefore should not be construed as being limiting inany way.

The location database 130 can be updated by the virtual mobilemanagement entity data 128. In particular, the location database 130 canindicate geographic locations of components and/or entities of orassociated with the mobile management entity pools 108. As such, thevirtual mobile management entity data 128 can be used to update thelocation database 130 to include the new virtual mobile managemententity 118N and/or to indicate the geographic location of the newvirtual mobile management entity 118N. The location database 130 alsocan be queried by way of the virtual mobile management entity data 128to determine other elements associated with the geographic location ofthe new virtual mobile management entity 118N. In particular, thelocation database 130 can be queried using the virtual mobile managemententity data 128 to determine a mobile management entity pool 108 inwhich the new virtual mobile management entity 118N is located and/orother elements associated with that mobile management entity pool 108.

According to various embodiments, the orchestrator application 106 canalso obtain, in response to submitting the virtual mobile managemententity data 128, one or more workflows 134 associated with the mobilemanagement entity pool 108 to which the new virtual mobile managemententity 118N belongs. The workflows 134 can identify pool elements (e.g.,entities in the core 116, virtual mobile management entities 118,eNodeBs 120, and the like) and provide information that can be used bythe orchestrator application 106 to instantiate signaling between and/oramong these pool elements and the new virtual mobile management entity118N. In some contemplated embodiments, the workflows 134 can includedirected graphs that can be executed or processed by various entities(e.g., the EMS entities) to instantiate and/or configure peer nodes, toestablish signaling over specific interfaces, combinations thereof, orthe like. According to various embodiments of the concepts andtechnologies described herein, the pool elements can include one or morepeer nodes associated with the new virtual mobile management entity118N. It should be understood that this example is illustrative andtherefore should not be construed as being limiting in any way.

As such, it can be appreciated that in response to receiving theactivation request 124, the orchestrator application 106 can obtain theworkflows 134 from the data store 132. More details of how the workflows134 are used by the orchestrator application 106 will be provided below.As shown in FIG. 1, however, it can be appreciated that the orchestratorapplication 106 can forward the workflows 134 to the eNodeB EMS 112and/or other EMS 114.

The other EMS 114 can receive the workflows 134 from the orchestratorapplication 106 and create core commands 136. The core commands 136 canbe sent to each of the peer nodes of the new virtual mobile managemententity 118N. The core commands 136 can include configuration informationthat can be used by the peer nodes to establish signaling between thepeer nodes and the new virtual mobile management entity 118N. Thus, itcan be appreciated that the core commands 136 can prepare the peer nodesof the new virtual mobile management entity 118N for signaling with thepeer nodes.

The eNodeB EMS 112 can create signaling commands 138. The signalingcommands 138 can be sent by the eNodeB EMS 112 to setup the signalingbetween the eNodeBs 120, the new virtual mobile management entity 118N,and the various pool elements of the mobile management entity pool 108.Thus, it can be appreciated that the orchestrator application 106 caninstantiate the signaling between various elements of the mobilemanagement entity pool 108 and/or the new virtual mobile managemententity 118N by way of providing the workflows 134 to one or more the EMSentities. It should be understood that this example is illustrative andtherefore should not be construed as being limiting in any way.

Because signaling can be instantiated between the new virtual mobilemanagement entity 118N and other pool elements via workflows 134 thatare identified based on the geographic location of the new virtualmobile management entity 118N, the signaling can be instantiated in amatter of minutes. These workflows 134 therefore can provide benefitssuch as short setup times for virtual mobile management entities 118added to mobile management entity pools 108 and/or quick activation ofnew virtual network functions that may be embodied by the virtual mobilemanagement entities 118. It should be understood that this example isillustrative and therefore should not be construed as being limiting inany way.

According to various embodiments of the concepts and technologiesdescribed herein, the workflows can establish the signaling between thepeer nodes and the new virtual mobile management entity 118N overspecific interfaces. In particular, the workflows can be used toestablish signaling between eNodeBs 120 and/or other elements of themobile management entity pools 108 using and/or via specific interfacesassociated with the mobile management entity pools 108. TABLE 1 shows alist of example interfaces over which the signaling can be establishedin accordance with various embodiments of the concepts and technologiesdescribed herein. It should be understood that this list of interfacesis not exhaustive and therefore should be viewed as illustrative and notlimiting in any way.

TABLE 1 vMME 3GPP 3GPP peer (3GPP) Interface Node Layer 4/3 Details vMMES1-MME eNB SCTP/IP Signaling vMME M3 eNB SCTP/IP eMBMS signaling vMMES6a DRA/HSS Diameter/SCTP/IP Signaling vMME SLg DRA/GMLCDiameter/SCTP/IP Signaling vMME SLs ESMLC SCTP/IP Signaling vMME SBc BMCSCTP/IP Signaling vMME SGs MSC SCTP/IP Signaling vMME Sm eMBMS GWGTPv2c/IP Signaling vMME S11 S-GW GTPv2c/IP Signaling vMME S3 S4 SGSNGTPv2c/IP Signaling vMME S10 vMME/MME GTPv2c/IP Signaling vMME Gn SGSNGTPv1/IP Signaling vMME Sv MSC GTPv2c/IP Signaling vMME DNS DNSUDP/TCP/IP Signaling vMME X2 Lawful TCP Signaling Interception GW vMMENTP/Node NTP/Network TCP Signaling Statistics Statistics Real time

In practice, a virtual mobile management entity 118 can be instantiatedfor various purposes. According to various embodiments, the virtualmobile management entity 118 can be instantiated to support particularfunctionality, to meet demand changes, combinations thereof, or thelike. The virtual mobile management entity 118 can be registered with anetwork, and a request such as an activation request 124 or otherrequest can be generated to inform an orchestrator application 106 orother functionality that the virtual mobile management entity 118 hasbeen instantiated and registered. The activation request 124 also canspecify a geographic location associated with the virtual mobilemanagement entity 118.

The orchestrator application 106 can analyze the activation request 124to identify the geographic location of the virtual mobile managemententity 118. The orchestrator application 106 can query or otherwisesearch a location database 130 based on the determined geographiclocation. In some embodiments, the orchestrator application 106 cangenerate virtual mobile management entity data 128 that can capture thegeographic location and submit the virtual mobile management entity data128 to the location database 130. It should be understood that thisexample is illustrative and therefore should not be construed as beinglimiting in any way.

The orchestrator application 106 can receive a result set or otherresults that can identify one or more entities associated with thegeographic location associated with the virtual mobile management entity118. The identified elements can include other pool elements associatedwith the location of the virtual mobile management entity 118 andtherefore can include peer elements and/or peer nodes associated withthe virtual mobile management entity 118. The orchestrator application106 also can obtain workflows 134 and/or configurations that can specifyhow signaling is to be established for the identified peer nodes (orother pool elements) and the virtual mobile management entity 118.

The orchestrator application 106 can forward the workflows 134 tovarious entities associated with the mobile management entity pool 108in which the virtual mobile management entity 118 was instantiated. Thesignaling between the virtual mobile management entity 118 and the peernodes can be established by one or more EMS entities 110, 112, 114 usingthe workflows, if desired. Thus, embodiments of the concepts andtechnologies described herein can enable setup of signaling for virtualmobile management entities 118 using only geographic locationinformation associated with a newly instantiated virtual mobilemanagement entity 118. These and additional features of the concepts andtechnologies described herein will be illustrated and described in moredetail below.

FIG. 1 illustrates one server computer 102, one network 104, threemobile management entity pools 108, and one data store 132. It should beunderstood, however, that various implementations of the operatingenvironment 100 can include zero, one, or more than one server computer102; zero, one, or more than one network 104; zero, one, two, three, ormore than three mobile management entity pools 108; and/or zero, one, ormore than one data store 132. As such, the illustrated embodiment shouldbe understood as being illustrative, and should not be construed asbeing limiting in any way.

Turning now to FIG. 2, aspects of a method 200 for initiating signalingassociated with a virtual mobility management entity will be describedin detail, according to an illustrative embodiment. It should beunderstood that the operations of the methods disclosed herein are notnecessarily presented in any particular order and that performance ofsome or all of the operations in an alternative order(s) is possible andis contemplated. The operations have been presented in the demonstratedorder for ease of description and illustration. Operations may be added,omitted, and/or performed simultaneously, without departing from thescope of the concepts and technologies disclosed herein.

It also should be understood that the methods disclosed herein can beended at any time and need not be performed in its entirety. Some or alloperations of the methods, and/or substantially equivalent operations,can be performed by execution of computer-readable instructions includedon a computer storage media, as defined herein. The term“computer-readable instructions,” and variants thereof, as used herein,is used expansively to include routines, applications, applicationmodules, program modules, programs, components, data structures,algorithms, and the like. Computer-readable instructions can beimplemented on various system configurations including single-processoror multiprocessor systems, minicomputers, mainframe computers, personalcomputers, hand-held computing devices, microprocessor-based,programmable consumer electronics, combinations thereof, and the like.

Thus, it should be appreciated that the logical operations describedherein are implemented (1) as a sequence of computer implemented acts orprogram modules running on a computing system and/or (2) asinterconnected machine logic circuits or circuit modules within thecomputing system. The implementation is a matter of choice dependent onthe performance and other requirements of the computing system.Accordingly, the logical operations described herein are referred tovariously as states, operations, structural devices, acts, or modules.These states, operations, structural devices, acts, and modules may beimplemented in software, in firmware, in special purpose digital logic,and any combination thereof. As used herein, the phrase “cause aprocessor to perform operations” and variants thereof is used to referto causing a processor of a computing system or device, such as theserver computer 102 to perform one or more operations and/or causing theprocessor to direct other components of the computing system or deviceto perform one or more of the operations.

For purposes of illustrating and describing the concepts of the presentdisclosure, the methods disclosed herein are described as beingperformed by the server computer 102 via execution of one or moresoftware modules such as, for example, the orchestrator application 106.It should be understood that additional and/or alternative devicesand/or network nodes can provide the functionality described herein viaexecution of one or more modules, applications, and/or other softwareincluding, but not limited to, the orchestrator application 106. Thus,the illustrated embodiments are illustrative, and should not be viewedas being limiting in any way.

The method 200 begins at operation 202. At operation 202, the servercomputer 102 can receive an activation request associated with a virtualmobile management entity 118. According to various embodiments, theactivation request received in operation 202 can be similar or evenidentical to the activation request 124 illustrated and described abovewith reference to FIG. 1. As such, it can be appreciated that theactivation request 124 can be obtained by the server computer 102 via anAPI 126, though this is not necessarily the case. Furthermore, it can beappreciated that the activation request 124 can include geographiclocation data that identifies a geographic location associated with thevirtual mobile management entity 118. The activation request 124 alsocan include an indication that one or more virtual mobile managemententity 118 has been instantiated and registered. It should be understoodthat this example is illustrative and therefore should not be construedas being limiting in any way.

From operation 202, the method 200 can proceed to operation 204. Atoperation 204, the server computer 102 can add the virtual mobilemanagement entity 118 associated with the activation request received inoperation 202 to a database. In various embodiments, the server computer102 can add data describing the virtual mobile management entity 118 toa location database such as the location database 130 illustrated anddescribed in FIG. 1. The location database 130 can include a topology ofthe mobile management entity pools 108, as well as location informationidentifying geographic locations of one, more than one, and/or allelements of the mobile management entity pools 108.

According to various embodiments, names of the pool elements can includea common language location identifier (“CLLI”) and/or other informationthat can identify the geographic locations of the pool elements.According to various embodiments of the concepts and technologiesdescribed herein, the virtual mobile management entities 118 can benamed such that a portion of the name identifies a respective geographiclocation of the virtual mobile management entities 118. Because thelocations of elements of the mobile management entity pools 108 can beidentified and/or represented in additional and/or alternative ways, itshould be understood that these examples are illustrative and thereforeshould not be construed as being limiting in any way.

From operation 204, the method 200 can proceed to operation 206. Atoperation 206, the server computer 102 can determine a geographiclocation associated with the virtual mobile management entity 118associated with the activation request received or otherwise obtained inoperation 202. According to various embodiments, the server computer 102can extract the geographic location from the activation request 124. Insome other embodiments, the server computer 102 can query the locationdatabase 130 and receive the geographic location in response to thequery. In some embodiments, for example, the server computer 102 cangenerate virtual mobile management entity data 128 and use the virtualmobile management entity data 128 to query the location database 130 toobtain the location information associated with the virtual mobilemanagement entity 118. Because the location of the virtual mobilemanagement entity 118 can be determined in additional and/or alternativemanners, it should be understood that these examples are illustrativeand therefore should not be construed as being limiting in any way.

From operation 206, the method 200 can proceed to operation 208. Atoperation 208, the server computer 102 can map the location of thevirtual mobile management entity 118 determined in operation 206 to thelocation database 130. In some embodiments, the server computer 102 canquery the location database 130 using the location determined inoperation 206 and/or otherwise match or map data in the locationdatabase 130 to the location determined in operation 206. In someembodiments, for example, the server computer 102 can query the locationdatabase 130 using the location determined in operation 206, and thedata store 132 (or other entity) can return a result set that includesany pool elements that correspond to the location used to query thelocation database 130.

An example of mapping locations using the location database 130 isschematically shown in FIG. 7. As shown, the location database 130 caninclude one or more tables of data, and the multiple tables can includeand/or represent location information, pool element identifiers (e.g.,CLLI names, or other identifiers), and the like. As shown in FIG. 7, thegeographic location information can be provided as latitude andlongitude information, though this example is illustrative. In mappinglocations, the server computer 102 can identify a geographic location ofone or more entities (e.g., the virtual mobile management entity 118named BELWA001) and identify other pool elements associated with thatlocation. As shown in FIG. 7, other pool elements associated with thegeographic location of the virtual mobile management entity 118 namedBELWA001 include the virtual mobile management entities 118 namedBELWA002 and BELWA03, the 3GPP nodes REDWA001 and REDWA002, and eNodeBs120 with CLLI names SEAWA001, SEAWA002, SEAWA003, SEAWA004, andSEAWA005. Because identifying elements associated with a particularlocation can be done in additional and/or alternative manners, it shouldbe understood that this example is illustrative and therefore should notbe construed as being limiting in any way.

From operation 208, the method 200 can proceed to operation 210. Atoperation 210, the server computer 102 can identify one or more elementsof a mobile management entity pool 108 in which the virtual mobilemanagement entity 118 is located. It can be appreciated that the one ormore elements can be identified from a result set (if a result set isprovided in operation 208) and/or otherwise identified from the locationdatabase 130. In operation 210, the server computer 102 can identifypeer nodes for the virtual mobile management entity 118. Thus, operation210 can result in a list of peer nodes of the virtual mobile managemententity 118 for which signaling is to be initiated as illustrated anddescribed herein. It should be understood that this example isillustrative and therefore should not be construed as being limiting inany way.

In some embodiments of operation 210, the server computer 102 can obtaina list of pool elements (e.g., peer nodes) as a result set. Thus, theserver computer 102 can use the geographic location determined inoperation 206 to identify one or more pool elements (e.g., peer nodes)associated with a particular location and therefore the virtual mobilemanagement entity 118 associated with the activation request 124received in operation 202. Because the pool elements associated with aparticular location and/or virtual mobile management entity 118 can bedetermined in additional and/or alternative manners, it should beunderstood that this example is illustrative and therefore should not beconstrued as being limiting in any way.

From operation 210, the method 200 can proceed to operation 212. Atoperation 212, the server computer 102 can obtain workflows 134 andconfigurations associated with one or more of the pool elementsidentified in operation 210. Thus, in operation 212 the server computer102 can receive configurations for the peer nodes or other pool elementsidentified in operation 210, as well as workflows 134 that can be usedto establish signaling as illustrated and described herein. As explainedabove, the workflows 134 can detail signaling to be set up for each ofthe pool elements, interfaces to be used for the signaling, combinationsthereof, or the like. It should be understood that these examples areillustrative and therefore should not be construed as being limiting inany way.

From operation 212, the method 200 can proceed to operation 214. Atoperation 214, the server computer 102 can send the configurations andthe workflows 134 obtained in operation 212 to the EMS entities (e.g.,the eNodeB EMS 112 and the other EMS 114). The EMS entities can use theworkflows 134 and the configurations to configure the pool elements(e.g., peer nodes of the virtual mobile management entity 118) and/or toestablish signaling between the pool elements and the virtual mobilemanagement entity 118. It can be appreciated that in some embodiments ofthe concepts and technologies described herein, the EMS entities canestablish the signaling over the particular interfaces as illustratedand described above, and as such the functionality of operation 214 caninclude the server computer 102 sending the configurations and/orworkflows to the EMS entities. Thus, the server computer 102 can performoperations 202-214 to initiate signaling between a virtual mobilemanagement entity 118 and peer nodes of the virtual mobile managemententity 118, in some embodiments.

From operation 214, the method 200 can proceed to operation 216. Themethod 200 can end at operation 216.

Turning now to FIG. 3, aspects of a method 300 for updating signalingassociated with a virtual mobility management entity will be describedin detail, according to an illustrative embodiment. The method 300 canbegin at operation 302. At operation 302, the server computer 102 candetermine a geographic location of an eNodeB 120. According to variousembodiments of the concepts and technologies described herein, theeNodeBs 120 can be a mobile eNodeB 120 and therefore can have ageographic location that can change over time. For example, thefunctionality of the eNodeBs 120 can be provided by one or more drones,one or more mobile vehicles, one or more satellites, combinationsthereof, or the like, wherein these or other types of entities can movewith respect to geographic location over time. Thus, the location of theeNodeBs 120 can be monitored to determine if and when the eNodeBs 120leave a region served by a mobile management entity pool 108 orotherwise move to a new geographic location.

FIG. 4 schematically illustrates an example of an eNodeB 120 moving froma first geographic location 400 to a second geographic location 402. Asshown in FIG. 4, the first geographic location 400 may be served by afirst mobile management entity pool 108A, and the second geographiclocation 402 may be served by a second mobile management entity pool108B. Thus, the eNodeB 120 may move from the first mobile managemententity pool 108A to the second mobile management entity pool 108B by wayof moving from the first geographic location 400 to the secondgeographic location 402. It should be understood that this example isillustrative and therefore should not be construed as being limiting inany way.

From operation 302, the method 300 can proceed to operation 304. Atoperation 304, the server computer 102 can determine if the eNodeB 120has moved out of a mobile management entity pool 108 with which theeNodeB 120 is associated. According to various embodiments, the servercomputer 102 can query the location database 130 with informationidentifying the eNodeB 120 and obtain a location associated with theeNodeB 120. The server computer 102 can compare the location obtainedfrom the location database 130 to the location determined in operation302 and determine if the locations match. If the locations do not match,the server computer 102 can determine that the eNodeB 120 has moved outof an associated mobile management entity pool 108. Because the servercomputer 102 can determine that the eNodeB 120 has moved out of a mobilemanagement entity pool 108 in additional and/or alternative manners, itshould be understood that this example is illustrative and thereforeshould not be construed as being limiting in any way.

It should be appreciated that in some embodiments of the method 300, theserver computer 102 can determine if the eNodeB 120 has moved to a newgeographic location instead of, or in addition to, determining if theeNodeB 120 has moved out of a mobile management entity pool 108. Assuch, the embodiment of the method 300 illustrated and described in FIG.3 is illustrative and should not be construed as being limiting in anyway.

If the server computer 102 determines, in operation 304, that the eNodeB120 has not moved out of the mobile management entity pool 108, themethod 300 can return to operation 302, and the server computer 102 canagain determine a geographic location associated with the eNodeB 120. Ittherefore can be appreciated that operations 302-304 can be repeateduntil the server computer 102 determines, in any iteration of operation304, that the eNodeB 120 has moved out of the mobile management entitypool 108. If the server computer 102 determines, in operation 304, thatthe eNodeB 120 has moved out of the mobile management entity pool 108,the method 300 can proceed to operation 306.

At operation 306, the server computer 102 can identify a mobilemanagement entity pool 108 associated with the geographic locationdetermined in operation 302. In some embodiments, the server computer102 can query the location database 130 using the geographic locationdetermined in operation 302, and receive, in response to the query,identification of the mobile management entity pool 108 associated withthe location. Because the mobile management entity pool 108 can beidentified in additional and/or alternative manners, it should beunderstood that this example is illustrative and therefore should not beconstrued as being limiting in any way.

In operation 308, the server computer 102 can add the eNodeB 120 to themobile management entity pool 108 identified in operation 306. Thus, theserver computer 102 can update the location database 130 in operation308 with data identifying the eNodeB 120 to indicate that the eNodeB 120is now located in a region or location served by the mobile managemententity pool 108 identified in operation 306.

From operation 308, the method 300 can proceed to operation 210 of themethod 200 illustrated in FIG. 2, as illustrated in FIG. 3. Thus, it canbe appreciated that the eNodeB 120 can be moved into a new mobilemanagement entity pool 108 and the signaling for that eNodeB 120 can beestablished as explained above with reference to FIG. 2.

According to various embodiments of the concepts and technologiesdescribed herein, the functionality illustrated and described herein canbe used to provide use SDN techniques to create wireless signalgenerating networks on demand and/or to create on-demand services. Somecontemplated embodiments of how the concepts and technologies describedherein can be used are provided below.

In one contemplated embodiment, the concepts and technologies describedherein can be used to enable attachment of groups of machine-to-machine(“M2M”) devices to a network for various purposes. For example, a largegroup of M2M devices may need to attach to a network (e.g., an LTEnetwork) to establish communication, to provide one or more emergencynotifications, to deliver data (e.g., an emergency patch or softwareupgrade), or the like. Such an attachment of a large group of devicescould affect the network negatively (e.g., consume signaling resourcesof the network reducing the ability of other users from attaching and/orusing the network, etc.). Such traffic saturation also could affectservice for many or even all users, thereby negatively impacting thenetwork as a whole. Thus, some embodiments of the concepts andtechnologies described herein enable dynamic instantiation of virtualmobile management entities 118 to accommodate provisioning andconnectivity with peer nodes to enable flexible capacity control ofwireless signaling networks to allow service delivery and/or continuityduring spikes and/or lulls in demand.

Thus, in some embodiments of the concepts and technologies describedherein, the functionality illustrated and described herein for receivingan activation request 124 can identify or specify a group of M2M devicesthat are to be instantiated, a size of the group, and a geographiclocation associated with one or more members of the M2M devices. Theactivation request 124 also can identify one or more virtual mobilemanagement entities 118 that are to be (or have been) activated to meetthe needs of the group of M2M devices and one or more associatedgeographic locations. Additionally, or alternatively, the activationrequest 124 can specify an expected duration of the attachment of theM2M devices, and as such, a duration of the signaling established by wayof the functionality illustrated and described herein can specified bythe activation request. It should be understood that this example isillustrative and therefore should not be construed as being limiting inany way.

In another contemplated embodiment, concepts and technologies describedherein, the signaling can be established to support a broadcast ofmessages, alerts, or the like. For example, an emergency situation(natural or otherwise) may prompt delivery of emergency messages orservices to specific locations (e.g., locations affected by theemergency situation, other locations, etc.). The concepts andtechnologies described herein can be used to quickly establish signalingfor new virtual mobile management entities 118 created to support theseneeds. Furthermore, because the geographic area or region that is toreceive the services may span over two or more mobile management entitypools 108, two or more virtual mobile management entities 118 may becreated to support the broadcast messages contemplated herein.

Thus, some embodiments of the concepts and technologies described hereincan instantiate new virtual mobile management entities 118 and establishsignaling for the virtual mobile management entities 118 instead ofoverloading and/or overriding overload controls associated with existingresources. Thus, the activation request 124 illustrated and describedherein can specify an expected duration of the needed resources, anumber of resources needed, geographic locations associated with theresources, combinations thereof, or the like. Furthermore, after thebroadcast is completed, embodiments of the concepts and technologiesdescribed herein can effect teardown of the signaling and resources,thereby freeing resources for other purposes. It should be understoodthat this example is illustrative and therefore should not be construedas being limiting in any way.

In yet another contemplated embodiment, the signaling can be establishedto modify quality of service (“QoS”) attributes of specific signalingand/or resources associated with that signaling. Thus, whiletraditionally QoS policies may be present and/or configured for specificsignaling and/or resources, the concepts and technologies describedherein can establish signaling to establish or even modify QoSassociated with resources or the signaling itself. Thus, embodiments ofthe concepts and technologies described herein can use an activationrequest 124 to specify a QoS associated with particular signaling (e.g.,to specify configurations) or the like. Thus, the activation request 124can, in addition to requesting establishment of signaling as illustratedand described herein, specify, modify, or delete QoS policies andinternal configuration/provisioning attributes on demand. The QoSestablished by way of the activation request 124 can take into accountnetwork conditions, if desired. It should be understood that thisexample is illustrative and therefore should not be construed as beinglimiting in any way.

In still another contemplated embodiment, the concepts and technologiesdescribed herein can be used to establish and maintain signaling betweenmobile resources (e.g., drone based eNodeBs 120, or the like) asillustrated and described above with reference to FIG. 4. As such, theactivation request 124 illustrated and described herein can be receivedfrom various entities and, instead of specifying instantiation of avirtual mobile management entity 118, can specify that an eNodeB 120 orother resource has moved into a new geographic location (or is going tomove into the new geographic location). Thus, the activation request 124can effectively request establishment of signaling between a mobileeNodeB 120 and peer nodes in a mobile management entity pool 108 towhich the eNodeB 120 has moved. This activation request 124 cantherefore request establishment of a new virtual mobile managemententity 118 within the new mobile management entity pool 108, if desired.It should be understood that this example is illustrative and thereforeshould not be construed as being limiting in any way.

In another contemplated embodiment, the signaling can be established tosupport communications associated with a disaster situation or othertransient spike in demand. For example, a disaster situation may cause aspike in demand at a particular geographic location. To meet thisdemand, the concepts and technologies described herein can be used toestablish additional mobile management entity capacity and associatedsignaling. Thus, the activation request 124 can request provisioning ofa new virtual mobile management entity 118, addition of the virtualmobile management entity 118 to a particular mobile management entitypool 108, and establishment of signaling between the new virtual mobilemanagement entity 118 and peer nodes of the mobile management entitypool 108. Thus, embodiments of the concepts and technologies describedherein can reduce impact on customer service and/or experience, even incrisis or disaster situations, where adding physical network functionnodes and associated signaling may take weeks, by which time thedisaster or crisis situation may have ended. As such, the activationrequest 124 can specify a geographic location in which a virtual mobilemanagement entity 118 is to be instantiated and establish signalingbetween the new virtual mobile management entity 118 and the peer nodesin that mobile management entity pool 108. It should be understood thatthis example is illustrative and therefore should not be construed asbeing limiting in any way.

In yet another contemplated embodiment, the signaling can be establishedto support development and/or testing in a pre-deployment orpost-deployment environment. In particular, the concepts andtechnologies described herein can be used to support test interfacesthat can be used to support functions that are being tested. Thus, theactivation request 124 can specify virtual mobile management entities118 to be created, a duration of the testing (and therefore the life ofthe resources being created), and an identification of geographiclocations in which the virtual mobile management entities 118 are to becreated, and signaling to be established for those virtual mobilemanagement entities 118 and/or peer nodes in the mobile managemententity pool 108 associated with the virtual mobile management entity118. The new resources can be used for testing and torn down, ifdesired, after testing. It should be understood that this example isillustrative and therefore should not be construed as being limiting inany way.

Turning now to FIG. 5, additional details of the network 104 areillustrated, according to an illustrative embodiment. The network 104includes a cellular network 502, a packet data network 504, for example,the Internet, and a circuit switched network 506, for example, apublicly switched telephone network (“PSTN”). The cellular network 502includes various components such as, but not limited to, basetransceiver stations (“BTSs”), NodeBs or eNodeBs, base stationcontrollers (“BSCs”), radio network controllers (“RNCs”), mobileswitching centers (“MSCs”), mobile management entities (“MMEs”), shortmessage service centers (“SMSCs”), multimedia messaging service centers(“MMSCs”), home location registers (“HLRs”), home subscriber servers(“HSSs”), visitor location registers (“VLRs”), charging platforms,billing platforms, voicemail platforms, GPRS core network components,location service nodes, an IP Multimedia Subsystem (“IMS”), and thelike. The cellular network 502 also includes radios and nodes forreceiving and transmitting voice, data, and combinations thereof to andfrom radio transceivers, networks, the packet data network 504, and thecircuit switched network 506.

A mobile communications device 508, such as, for example, a cellulartelephone, a user equipment, a mobile terminal, a PDA, a laptopcomputer, a handheld computer, and combinations thereof, can beoperatively connected to the cellular network 502. The cellular network502 can be configured as a 2G GSM network and can provide datacommunications via GPRS and/or EDGE. Additionally, or alternatively, thecellular network 502 can be configured as a 3G UMTS network and canprovide data communications via the HSPA protocol family, for example,HSDPA, EUL (also referred to as HSDPA), and HSPA+. The cellular network502 also is compatible with 4G mobile communications standards as wellas evolved and future mobile standards.

The packet data network 504 includes various devices, for example,servers, computers, databases, and other devices in communication withone another, as is generally known. The packet data network 504 devicesare accessible via one or more network links. The servers often storevarious files that are provided to a requesting device such as, forexample, a computer, a terminal, a smartphone, or the like. Typically,the requesting device includes software (a “browser”) for executing aweb page in a format readable by the browser or other software. Otherfiles and/or data may be accessible via “links” in the retrieved files,as is generally known. In some embodiments, the packet data network 504includes or is in communication with the Internet. The circuit switchednetwork 506 includes various hardware and software for providing circuitswitched communications. The circuit switched network 506 may include,or may be, what is often referred to as a plain old telephone system(POTS). The functionality of a circuit switched network 506 or othercircuit-switched network are generally known and will not be describedherein in detail.

The illustrated cellular network 502 is shown in communication with thepacket data network 504 and a circuit switched network 506, though itshould be appreciated that this is not necessarily the case. One or moreInternet-capable devices 510, for example, a PC, a laptop, a portabledevice, or another suitable device, can communicate with one or morecellular networks 502, and devices connected thereto, through the packetdata network 504. It also should be appreciated that theInternet-capable device 510 can communicate with the packet data network504 through the circuit switched network 506, the cellular network 502,and/or via other networks (not illustrated).

As illustrated, a communications device 512, for example, a telephone,facsimile machine, modem, computer, or the like, can be in communicationwith the circuit switched network 506, and therethrough to the packetdata network 504 and/or the cellular network 502. It should beappreciated that the communications device 512 can be anInternet-capable device, and can be substantially similar to theInternet-capable device 510. In the specification, the network 104 isused to refer broadly to any combination of the networks 502, 504, 506.It should be appreciated that substantially all of the functionalitydescribed with reference to the network 104 can be performed by thecellular network 502, the packet data network 504, and/or the circuitswitched network 506, alone or in combination with other networks,network elements, and the like.

FIG. 6 is a block diagram illustrating a computer system 600 configuredto provide the functionality described herein for initiating signalingin mobile management entity pools using workflows, in accordance withvarious embodiments of the concepts and technologies disclosed herein.The computer system 600 includes a processing unit 602, a memory 604,one or more user interface devices 606, one or more input/output (“I/O”)devices 608, and one or more network devices 610, each of which isoperatively connected to a system bus 612. The bus 612 enablesbi-directional communication between the processing unit 602, the memory604, the user interface devices 606, the I/O devices 608, and thenetwork devices 610.

The processing unit 602 may be a standard central processor thatperforms arithmetic and logical operations, a more specific purposeprogrammable logic controller (“PLC”), a programmable gate array, orother type of processor known to those skilled in the art and suitablefor controlling the operation of the server computer. As used herein,the word “processor” and/or the phrase “processing unit” when used withregard to any architecture or system can include multiple processors orprocessing units distributed across and/or operating in parallel in asingle machine or in multiple machines. Furthermore, processors and/orprocessing units can be used to support virtual processing environments.Processors and processing units also can include state machines,application-specific integrated circuits (“ASICs”), combinationsthereof, or the like. Because processors and/or processing units aregenerally known, the processors and processing units disclosed hereinwill not be described in further detail herein.

The memory 604 communicates with the processing unit 602 via the systembus 612. In some embodiments, the memory 604 is operatively connected toa memory controller (not shown) that enables communication with theprocessing unit 602 via the system bus 612. The memory 604 includes anoperating system 614 and one or more program modules 616. The operatingsystem 614 can include, but is not limited to, members of the WINDOWS,WINDOWS CE, and/or WINDOWS MOBILE families of operating systems fromMICROSOFT CORPORATION, the LINUX family of operating systems, theSYMBIAN family of operating systems from SYMBIAN LIMITED, the BREWfamily of operating systems from QUALCOMM CORPORATION, the MAC OS, iOS,and/or LEOPARD families of operating systems from APPLE CORPORATION, theFREEBSD family of operating systems, the SOLARIS family of operatingsystems from ORACLE CORPORATION, other operating systems, and the like.

The program modules 616 may include various software and/or programmodules described herein. In some embodiments, for example, the programmodules 616 include the orchestrator application 106. This and/or otherprograms can be embodied in computer-readable media containinginstructions that, when executed by the processing unit 602, perform oneor more of the methods 200, 300 described in detail above with respectto FIGS. 2-3. According to embodiments, the program modules 616 may beembodied in hardware, software, firmware, or any combination thereof.Although not shown in FIG. 6, it should be understood that the memory604 also can be configured to store the request 124, the virtual mobilemanagement entity data 128, the location database 130, the workflows134, and/or other data, if desired.

By way of example, and not limitation, computer-readable media mayinclude any available computer storage media or communication media thatcan be accessed by the computer system 600. Communication media includescomputer-readable instructions, data structures, program modules, orother data in a modulated data signal such as a carrier wave or othertransport mechanism and includes any delivery media. The term “modulateddata signal” means a signal that has one or more of its characteristicschanged or set in a manner as to encode information in the signal. Byway of example, and not limitation, communication media includes wiredmedia such as a wired network or direct-wired connection, and wirelessmedia such as acoustic, RF, infrared and other wireless media.Combinations of the any of the above should also be included within thescope of computer-readable media.

Computer storage media includes volatile and non-volatile, removable andnon-removable media implemented in any method or technology for storageof information such as computer-readable instructions, data structures,program modules, or other data. Computer storage media includes, but isnot limited to, RAM, ROM, Erasable Programmable ROM (“EPROM”),Electrically Erasable Programmable ROM (“EEPROM”), flash memory or othersolid state memory technology, CD-ROM, digital versatile disks (“DVD”),or other optical storage, magnetic cassettes, magnetic tape, magneticdisk storage or other magnetic storage devices, or any other mediumwhich can be used to store the desired information and which can beaccessed by the computer system 600. In the claims, the phrase “computerstorage medium” and variations thereof does not include waves or signalsper se and/or communication media.

The user interface devices 606 may include one or more devices withwhich a user accesses the computer system 600. The user interfacedevices 606 may include, but are not limited to, computers, servers,personal digital assistants, cellular phones, or any suitable computingdevices. The I/O devices 608 enable a user to interface with the programmodules 616. In one embodiment, the I/O devices 608 are operativelyconnected to an I/O controller (not shown) that enables communicationwith the processing unit 602 via the system bus 612. The I/O devices 608may include one or more input devices, such as, but not limited to, akeyboard, a mouse, or an electronic stylus. Further, the I/O devices 608may include one or more output devices, such as, but not limited to, adisplay screen or a printer.

The network devices 610 enable the computer system 600 to communicatewith other networks or remote systems via a network, such as the network104. Examples of the network devices 610 include, but are not limitedto, a modem, a radio frequency (“RF”) or infrared (“IR”) transceiver, atelephonic interface, a bridge, a router, or a network card. The network104 may include a wireless network such as, but not limited to, aWireless Local Area Network (“WLAN”) such as a WI-FI network, a WirelessWide Area Network (“WWAN”), a Wireless Personal Area Network (“WPAN”)such as BLUETOOTH, a Wireless Metropolitan Area Network (“WMAN”) such aWiMAX network, or a cellular network. Alternatively, the network 104 maybe a wired network such as, but not limited to, a Wide Area Network(“WAN”) such as the Internet, a Local Area Network (“LAN”) such as theEthernet, a wired Personal Area Network (“PAN”), or a wired MetropolitanArea Network (“MAN”).

Based on the foregoing, it should be appreciated that systems andmethods for initiating signaling in mobile management entity pools usingworkflows have been disclosed herein. Although the subject matterpresented herein has been described in language specific to computerstructural features, methodological and transformative acts, specificcomputing machinery, and computer-readable media, it is to be understoodthat the concepts and technologies disclosed herein are not necessarilylimited to the specific features, acts, or media described herein.Rather, the specific features, acts and mediums are disclosed as exampleforms of implementing the concepts and technologies disclosed herein.

The subject matter described above is provided by way of illustrationonly and should not be construed as limiting. Various modifications andchanges may be made to the subject matter described herein withoutfollowing the example embodiments and applications illustrated anddescribed, and without departing from the true spirit and scope of theembodiments of the concepts and technologies disclosed herein.

1. A device comprising: a processor; and a memory that storescomputer-executable instructions that, when executed by the processor,cause the processor to perform operations comprising receiving locationdata that indicates a geographic location associated with a virtualmobile management entity, obtaining a mobile management entity topologythat defines boundaries of a plurality of mobile management entitypools, identifying, by the processor and based on the location data, aone of a plurality of mobile management entity pools in which thevirtual mobile management entity is located, identifying pool elementsincluded in the one of the plurality of mobile management entity pools,obtaining a workflow for establishing the pool elements, and requestingestablishment of signaling between the virtual mobile management entityand the pool elements.
 2. The device of claim 1, wherein the poolelements comprise peer nodes associated with the virtual mobilemanagement entity.
 3. The device of claim 1, wherein thecomputer-executable instructions, when executed by the processor, causethe processor to perform operations further comprising: detecting afirst geographic location associated with an eNodeB, the eNodeB beingassociated with the virtual mobile management entity; determining if thefirst geographic location associated with the eNodeB has changedrelative to a second geographic location associated with the eNodeB, thesecond geographic location being determined using a location database;and in response to determining that the first geographic location haschanged, identifying a new mobile management entity pool associated withthe first geographic location, and adding the eNodeB to the new mobilemanagement entity pool associated with the first geographic location. 4.The device of claim 3, wherein identifying the new mobile managemententity pool comprises mapping the first geographic location to a tablestored in the location database, and wherein the table identifies mobilemanagement entity pools and geographic locations associated with themobile management entity pools.
 5. The device of claim 1, wherein theworkflow is obtained from an element management system via anapplication programming interface exposed by the element managementsystem.
 6. The device of claim 1, wherein establishing the signalingcomprises sending, to the pool elements, configuration information usedto establish the signaling.
 7. A method comprising: receiving, by aprocessor that executes an orchestrator application, location data thatindicates a geographic location associated with a virtual mobilemanagement entity; obtaining, by the processor, a mobile managemententity topology that defines boundaries of a plurality of mobilemanagement entity pools; identifying, by the processor and based on thelocation data, one of a plurality of mobile management entity pools inwhich the virtual mobile management entity is located; identifying, bythe processor, pool elements included in the one of the plurality ofmobile management entity pools; obtaining, by the processor, a workflowfor establishing the pool elements; and requesting, by the processor,establishment of signaling between the virtual mobile management entityand the pool elements.
 8. The method of claim 7, further comprising:detecting a first geographic location associated with an eNodeB, theeNodeB being associated with the virtual mobile management entity;determining if the first geographic location associated with the eNodeBhas changed relative to a second geographic location associated with theeNodeB, the second geographic location being determined using a locationdatabase; and in response to determining that the first geographiclocation has changed, identifying a new mobile management entity poolassociated with the first geographic location, and adding the eNodeB tothe new mobile management entity pool associated with the firstgeographic location.
 9. The method of claim 8, wherein identifying thenew mobile management entity pool comprises mapping the first geographiclocation to a table stored in the location database, and wherein thetable identifies mobile management entity pools and geographic locationsassociated with the mobile management entity pools.
 10. The method ofclaim 7, wherein the workflow is obtained from an element managementsystem via an application programming interface exposed by the elementmanagement system.
 11. The method of claim 7, wherein the workflowcomprises a directed graph that is executed by an element managementsystem to establish the signaling.
 12. The method of claim 7, whereinestablishment of the signaling comprises sending, to the pool elements,configuration information that is used to establish the signaling. 13.The method of claim 7, wherein the location data is received with acommon language location identifier that identifies the virtual mobilemanagement entity.
 14. The method of claim 7, wherein the pool elementscomprise peer nodes associated with the virtual mobile managemententity.
 15. A computer storage medium having computer-executableinstructions stored thereon that, when executed by a processor, causethe processor to perform operations comprising: receiving location datathat indicates a geographic location associated with a virtual mobilemanagement entity; obtaining a mobile management entity topology thatdefines boundaries of a plurality of mobile management entity pools;identifying, by the processor and based on the location data, a one of aplurality of mobile management entity pools in which the virtual mobilemanagement entity is located; identifying pool elements included in theone of the plurality of mobile management entity pools; obtaining aworkflow for establishing the pool elements; and requestingestablishment of signaling between the virtual mobile management entityand the pool elements.
 16. The computer storage medium of claim 15,wherein the computer-executable instructions, when executed by theprocessor, cause the processor to perform operations further comprising:detecting a first geographic location associated with an eNodeB, theeNodeB being associated with the virtual mobile management entity;determining if the first geographic location associated with the eNodeBhas changed relative to a second geographic location associated with theeNodeB, the second geographic location being determined using a locationdatabase; and in response to determining that the first geographiclocation has changed, identifying a new mobile management entity poolassociated with the first geographic location, and adding the eNodeB tothe new mobile management entity pool associated with the firstgeographic location.
 17. The computer storage medium of claim 16,wherein identifying the new mobile management entity pool comprisesmapping the first geographic location to a table stored in the locationdatabase, and wherein the table identifies mobile management entitypools and geographic locations associated with the mobile managemententity pools.
 18. The computer storage medium of claim 15, wherein theworkflow is obtained from an element management system via anapplication programming interface exposed by the element managementsystem.
 19. The computer storage medium of claim 15, whereinestablishing the signaling comprises sending, to the pool elements,configuration information used to establish the signaling.
 20. Thecomputer storage medium of claim 15, wherein the pool elements comprisepeer nodes associated with the virtual mobile management entity.